• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    PRIORITY SIGNALING OVER A WIRELESS SERIAL COMMUNICATION CHANNEL A communication device performs a method for establishing a first path for signaling priority data. The method includes: establishing (202) a first short-range wireless data path to a second communication device for non-priority data exchange; and establishes (208) a second autonomous short-range wireless data path to the second communication device for exchanging priority data, wherein the second short-range wireless data path comprises such a wireless serial communication channel. as a Bluetooth radio frequency communication channel (RFCOMM). An application layer in an upper layer stack of the communication device establishes both the first and second short-range wireless data paths. Non-priority data communicated to the second communication device along the first short-range wireless data path is processed by the application layer. However, priority data communicated to the second communication device along the second short-range wireless data path bypasses the application layer.
    公开号:BR112012003047B1
    申请号:R112012003047-7
    申请日:2010-08-06
    公开日:2021-05-18
    发明作者:Robert J. Higgins；John B. Preston
    申请人:Motorola Solutions, Inc.；
    IPC主号:
    专利说明:

    The present application pertains to the following United States Commonly Owned Application in conjunction with this application by Motorola, Inc.: Serial No. 12/538,458 filed August 10, 2009 entitled "Methods and Apparatus for Communicating a Push-to -talk State to a Communication Device" Preston et al. (Attorney file number CM 12149). TECHNICAL FIELD
    The technical field generally refers to communication devices coupled over a short-range wireless link and more specifically to faster priority data signaling over the short-range wireless link. BACKGROUND
    In some communication scenarios, a communication device such as a two-way radio can be wirelessly coupled via a short-range wireless link (such as a Bluetooth link) to a peripheral device that has buttons, indicators, and the like. features such as a push button to talk PTT) to activate a PTT feature on the radio. In such a case, the button states, indicator states, and the PTT state for the radio are sent wirelessly between the two devices using the short range wireless link. Some customers, such as public safety customers, want a very short latency period between a user pressing the PTT button on the peripheral device and a corresponding PTT command (eg PUSH PTT or RELEASE PTT) reaching the radio number, which cannot be performed on known systems. Low latency can be extremely important for a PUSH PTT, for example, because a latency that is too long can result in garbled voice if the user starts talking, but the radio has not been activated via PUSH PTT to enable transmission of all initial user voice messages; this could mean the difference between a user saying "don't shoot", and having a "shot" go off in the transmitted message.
    In known systems, much of the latency is caused by the peripheral device. For example, there may be a "lock" in the peripheral device that prevents the PTT status from being sent immediately, such as when the peripheral device has already started sending a message or has a data stream temporarily stored when the PTT button is pressed. In that case, the PTT indication must wait to be sent until the other message has been sent and/or the temporary store released; or the peripheral device would otherwise have to abandon the data currently being transmitted and/or temporarily stored in a raw form. Additional extra code in the upper layers of the peripheral device can further increase the latency of PTT state transmission. For example, a Bluetooth integrated circuitry with a Virtual Machine (VM) in a headset or small PTT device has so much extra code in the upper layers that the latency from the moment the PTT button is pressed on the device peripheral until the time the PTT message is received in the radio's Bluetooth controller can be in the order of 100-400 ms; Bluetooth chip sets without VM can still incur latency of approximately 70-120 ms. A wireless adapter on the radio side also increases the latency of the PTT state reaching the core of the radio due to the decoding process within the upper layers of the wireless adapter software stack on the radio side - especially if the wireless adapter on the radio side The radio manages multiple Bluetooth profiles for multiple peripheral devices attached to the radio, which increases the processor load required to manage the various corresponding data messages and forward them to the appropriate destinations.
    Thus, there is a need for a mechanism to reduce latency in high priority data communication, such as a PTT state, from a peripheral device to a wireless-coupled communication device. BRIEF DESCRIPTION OF THE FIGURES
    The attached figures, where similar reference numerals refer to identical or functionally similar elements throughout separate views, which together with the detailed description below are incorporated and form part of the descriptive report and serve to further illustrate the various modalities of the concepts that include the claimed invention, and to explain the various principles and advantages of those embodiments.
    Figure 1 is a block diagram illustrating a system that includes a communication device and peripheral, which implements methods according to some embodiments.
    Figure 2 is a flow diagram of a method for priority signaling over a wireless serial communication channel according to some embodiments.
    Figure 3 is a block diagram illustrating coded priority messages being sent by a Bluetooth subsystem in a peripheral device over a wireless serial communication channel and decoded in a Bluetooth subsystem by the side of a radio according to some modalities.
    Figure 4 is a block diagram illustrating coded priority messages being sent by a Bluetooth subsystem in a peripheral device over a wireless serial communication channel and decoded in a Bluetooth subsystem by the side of a radio according to some embodiments.
    Figure 5 is a table illustrating a nibbler protocol format according to some embodiments.
    Figure 6 is a table illustrating exemplary headset protocol states according to some embodiments.
    Figure 7 is a table illustrating an exemplary null message according to some embodiments.
    Figure 8 is a table illustrating exemplary messages with buttons and battery states according to some embodiments. DETAILED DESCRIPTION
    Generally speaking, according to the various embodiments, a communication device performs a method for establishing a fast path for signaling priority data. The method includes: establishing a first short-range wireless data path to a second communication device for exchanging non-priority data; and establishes a second autonomous short-range wireless data path to the second communication device for exchanging priority data, wherein the second short-range wireless data path comprises a wireless serial communication channel such as a Bluetooth radio frequency communication channel (RFCOMM). An application layer in a stack of upper layers of the communication device establishes both the first and second short-range wireless data paths. Non-priority data communicated to the second communication device along the first short-range wireless data path is processed by the application layer. However, priority data communicated to the second communication device along the second short-range wireless data path bypasses the application layer, which has been shown to reduce latency by an average of approximately 50 ms. Those skilled in the art will appreciate that the above recognized advantages and other advantages described herein are illustrative only and are not intended to be a complete presentation of all the advantages of the various modalities.
    Referring now to the drawings, and particularly to Figure 1, a block diagram illustrating a system that includes two devices that communicate priority data, such as PTT state and noise state, according to some embodiments is shown and indicated generally at 100 System 100 includes a first communication device 102 (in this case a radio with a Bluetooth wireless "master" device, which is also simply referred to herein as a radio) and a second communication device 104 (in this case a device " Bluetooth wireless accessory slave" also referred to here as a peripheral device). The master device receives PTT commands from the slave device, where the devices, master and slave, can individually be any type of wireless communication device operating over one or more short-range wireless links and including a PTT resource. In addition, device 102 is equipped with equipment for transmitting and receiving media such as voice, data, and video to another communication device (not shown). Accordingly, device 102 can be, but is not limited to, a terrestrial mobile radio, a cellular phone, a personal data assistant (PDA), a personal computer, and the like, with a PTT application. Device 104 may be, but is not limited to, an accessory such as a headphone or headset, etc., which has a PTT button and may also be equipped with equipment for transmitting and receiving media and/or configured for other functionality.
    Priority data, as that term is used herein, means the data that a sending device selects to send along an end-to-end communication path faster than a communication path used to send non-priority data. Priority data includes, for example, time-sensitive data, data whose delivery is of greater importance than non-priority data, and the like. Push to talk, as that term is used herein, means a feature implemented in a communication device to enable users to talk over simplex or semi duplex communication paths, where during a call only one person at a time receives the 10 resources to talk, while all other parties on the call listen. An exemplary implementation of PTT technology is cellular PTT (also abbreviated and known in the industry as PoC), where the PTT capability is provided over a cellular network. Open 15 Mobile Alliance (OMA), which is a standards body that develops open standards for the mobile industry, is defining PoC as part of an IP Multimedia Subsystem, which is an architectural framework for providing Protocol multimedia services Internet. The 20 most recently released standards for the PoC feature are defined in a group of documents referred to as OMA PoC v 2.0, dated 6 August 2008.
    Device 102 comprises: a microcontroller or digital signal processor (DSP) 106; equipment for 25 short-range communications over a short-range wireless link 122 (wherein a short-range wireless link means a wireless connection that enables two devices to communicate using radio frequency (RF) resources over distances of approximately 100 m 30 (300 ft) or less, and in an illustrative example between 10-100 m or 30-300') using electromagnetic signals, which in this case is the Bluetooth device that includes an integrated circuit chip (IC) Bluetooth 108 with a corresponding antenna 110 that can be built-in to the radio or 5 included in an external adapter that connects to the radio; and a radio core 118 (which includes, for example, a two-way land mobile radio transceiver and a host processor for implementing processes within the radio core) with a corresponding antenna 120 which is activated by a PTT resource to transmit and receiving at least voice media over a wireless link 126. The device 104 comprises: a microcontroller or DSP 132; corresponding Bluetooth apparatus which includes a Bluetooth IC chip 128 with a corresponding antenna 130; and 15 other ancillary functions 140.
    In one embodiment, when a user turns peripheral device 104 ON, devices 102 and 104 perform a pairing procedure to associate peripheral device 104 with device 102. When radio 102 and peripheral device 104 store their respective numerical credentials for pairing , the devices are "paired", and the Bluetooth IC chips 108 and 128 operate to establish a short-range 122 Bluetooth wireless link for Bluetooth transmissions such as 25 voice transmissions and other data such as PTT status, status of other buttons, and indicators, etc., between the peripheral device 104 (e.g. a headphone or headset) and the radio 102.
    The Bluetooth IC chips 108 and 128 include at least 30: Bluetooth hardware (eg, radio frequency hardware number comprising a Bluetooth transceiver and baseband processor); Bluetooth firmware (for example, which implements lower layers of a multi-layered Bluetooth protocol stack that controls real-time and timely management of formatting and data flow needed to support the underlying Bluetooth protocol); and a microprocessor that is programmed with software and code stored in the device's memory on the chip. The Bluetooth hardware, firmware, microprocessor and/or software and code are communicatively coupled and configured to implement the Bluetooth protocol in accordance with one or more of: Bluetooth Specification 1.1 ratified as IEEE Standard 802.15.1-2002; Bluetooth Specification 1.2 ratified to the IEEE 802.15.1-2005 standard; Bluetooth Specification 2.0 + EDR (Optimized Data Rate) release November 10, 2004; Bluetooth Core Specification 2.1 adopted by Bluetooth SIG on July 26, 2007; Bluetooth 3.0 specification adopted by Bluetooth SIG on April 21, 2009; and/or subsequent versions of the Bluetooth Specification.
    The location within the Bluetooth device of the upper layers of the Bluetooth stack (which controls, for example, user interface applications) depends on whether the Bluetooth device is implemented as an HCI (Host/Controller Interface) system or a non-HCI system . In a non-HCI system, the upper layers of the Bluetooth stack are realized using the microprocessor residing in the Bluetooth chip. Whereas, in an HCI system, the upper layers of the Bluetooth stack are realized using a processing device that is external to the Bluetooth chip; and the upper and lower layers of the Bluetooth stack are coupled through a physical HCI data connection and communicate using a Bluetooth HCI protocol that is defined in the Bluetooth Specification.
    For example, where the Bluetooth apparatus in peripheral device 104 is implemented as an HCI system, the upper layers of the Bluetooth stack are implemented using the microcontroller 132, which is external to the Bluetooth chip 128; whereas in an HCI implementation, the upper layers of the stack are implemented within the Bluetooth chip 128. Where the Bluetooth device in the radio 102 is implemented as an HCI system, the upper layers of the Bluetooth stack are implemented using the microcontroller 106 or the computer processor. host on radio core 118, both of which are external to Bluetooth chip 108; whereas in a non-HCI implementation, the upper layers of the stack are implemented within the Bluetooth 108 chip. Microcontrollers 106 and 132 can also be used to perform other functionality including, but not limited to proprietary protocols such as the "nibbler" protocol described in detail below with reference to Figure 5-8 .
    In addition, the Bluetooth device in devices 102 and 104 may have a "symmetric" architecture or an "asymmetric" architecture. A symmetrical architecture means that the Bluetooth device of devices 102 and 104 are either implemented as HCI systems or are both implemented as non-HCI systems. An asymmetrical architecture means that the Bluetooth device in an 11
    device is implemented as an HCI system, and the other device's Bluetooth device is implemented as a non-HCI system.
    In accordance with the teachings provided herein, priority data is communicated wirelessly between peripheral device 104 and radio 102 in short-range transmissions over a short-range wireless link. In a specific embodiment, Bluetooth protocols are used to facilitate the transmission of priority data using the Bluetooth device on devices 102 and 104 as described, for example, with reference to Figures 2 to 4. However, in other embodiments other proprietary protocols may be used to transfer the priority data over the Bluetooth link as described, for example with reference to Figures 5 to 8. In addition, in the described modality, Bluetooth technology is used for short-range communications, but another technology could be used for short range communications including, but not limited to, Zigbee, IEEE 802.11 a/b/g (Wi-Fi), Wireless USB, etc. In such a case, priority data would be transferred in messages created using standard or proprietary protocols to facilitate the implementation of the alternative short-range communication technology.
    Furthermore, as the term is used herein, a multilayer protocol stack means a plurality of protocols that define a networking architecture for communication devices based on the Open Systems Interconnection (OSI) Reference Model, which divides the network architecture into seven 12 layers (ie Application, Presentation, Session, Transport, Network, Data Link and Physical) from top to bottom. Consequently, the two lower layers (also referred to here as the lower level or the lower 5 layers) mean the Data Link layers and
    Physical and associated protocols implemented to facilitate networking at these layers; and the upper layers (also referred to here as the upper or higher-level layers) means the Application, Presentation, Session, Transport, Networking layers and the associated protocols implemented to facilitate networking at these layers.
    With respect in addition to device 102, the transceiver (included in radio core 118) and antenna 120 15 are conventional elements that, in this illustrative embodiment, implement one or more protocols that enable the transmission and reception of voice media over the air with other devices. of communication (not shown). Such protocols may include, but are not limited to, the 20 standard specifications for wireless communications developed by standard entities such as TIA (Telecommunications Industry Association), OMA (Open Mobile Alliance), 3GPP (3rd Generation Partnership Project) , 3GPP2 (3rd Generation Partnership Project 2), IEEE 25 (Institute of Electrical and Electronics Engineers) 802, and WiMAX Forum. Still with respect to device 104, the other accessory functions 140 may include, but are not limited to, functions for headphones, car audio kits, keyboard and text display devices, 30 handheld computing devices, scanners, printers , and remote control devices.
    Turning now to Figure 2, there is shown a flow diagram of a method 200 for priority signaling over a wireless serial communication channel in accordance with some embodiments. Method 200 may be performed at peripheral device 104 or radio 102 to communicate priority data. For ease of understanding the implementation of method 200, this process will be described with reference to Figures 3 and 4, which show components and corresponding functionality of the Bluetooth device in a peripheral and radio device. In Figure 3, the Bluetooth device on the radio and peripheral device has an asymmetric architecture. In Figure 4, the Bluetooth device on the radio and peripheral device has a symmetrical architecture. It is further noted that, with respect to the present description, all blocks implemented by a processing device represent modules that are implemented by the processing device being programmed with relevant code (software and/or firmware).
    The apparatus 300 illustrated in Figure 3 comprises: a PTT button 302 (which indicates a state of PRESS PTT when a user presses a button, and RELEASE PTT when a user releases the button) coupled to a peripheral device Bluetooth chip 310 via an external microcontroller 304; a Bluetooth radio chip 330 communicatively coupled to peripheral device Bluetooth chip 310 via a Bluetooth wireless link 320; an external microcontroller 340 (which may comprise the host processor in the radio core or another microcontroller external to both chip
    Bluetooth 330 and host controller) communicatively coupled to Bluetooth radio chip 330 via an HCI 336; and optionally a hardware detector 360 coupled to the HCI 336.
    Peripheral device Bluetooth chip 310 comprises: an upper layer Bluetooth stack 312 that includes applications that interface with the user to communicate means such as user voice data; a 314 serial interface device, which in this case is a UART Universal Asynchronous Receiver/Transmitter) on chip, but can be any such device including, but not limited to, an RS-232C device, an SDIO (Protected Digital Input/Output), a USB (Universal Serial Bus), and the like, which is a physical hardware interface that converts the output bytes of data from the 304 microcontroller into a serial bit stream and converts the incoming data bits into data bytes for provide the microcontroller 3 04; and a Bluetooth radio and Bluetooth lower layer stack 316 which handles the modulation of data for transport over the Bluetooth wireless link 320 and the demodulation of data received from the Bluetooth wireless link 320. The Bluetooth radio chip 330 comprises a Bluetooth lower layer stack 332 and corresponding Bluetooth radio and a UART 334. The external microcontroller 340 comprises: a UART 342; a portion of the Bluetooth stack 344 (also referred to herein as the middle layer Bluetooth stack) that handles at least Bluetooth radio frequency communication protocol messages (RFCOMM) and can also run other transport and/or network layer protocols; an upper layer 15 Bluetooth stack 348 that includes at least the Application layer; a PTT decoder 350, and a noise state encoder 370.
    Apparatus 400 in Figure 4 comprises: a PTT button 402 coupled to a peripheral Bluetooth chip 410 via an external microcontroller 404; a Bluetooth radio chip 430 communicatively coupled with the peripheral device Bluetooth chip 410 via a Bluetooth wireless link 420; and an external microcontroller 10 440 communicatively coupled with the Bluetooth radio chip 430. The peripheral device Bluetooth chip 410 comprises: a top layer Bluetooth stack 412; a UART 414; and a 416 lower layer Bluetooth stack and Bluetooth radio. Bluetooth radio chip 15 430 comprises a lower layer Bluetooth stack and corresponding Bluetooth radio 432, a higher layer Bluetooth stack 434, and a UART 438.
    Turning now to Figure 2 and to the operation of apparatus 300 and 400 in accordance with the present teachings to communicate priority data between two wireless communication devices (e.g., a peripheral device and a radio). In the prior art, a problem contributing to latency in signaling time-sensitive events such as PTT states and noise states is that the path of this data includes the upper layer Bluetooth stack 312, 412, especially the layer. application, which adds processing time to signaling. However, in accordance with the present teachings, a second autonomous path is created that does not require priority data to be processed in the stack.
    Higher-layer or Bluetooth substantially minimizes such processing, thus minimizing latency for signaling time-sensitive events.
    To obtain such fast event signaling for time-sensitive events, during peripheral device startup and connection to the master Bluetooth device to form (202) the short-range Bluetooth wireless link 320, 420, the application layer of the top-level stack 312, 412 in the peripheral device creates (204) a short-range wireless data path that bypasses the upper layer Bluetooth stack 312, 412 and that includes a wireless serial communication channel. A short-range wireless path means a secure data path that is established using one or more wireless protocols and that includes a short-range wireless link.
    In this illustrative Bluetooth implementation, the top-layer Bluetooth stack 312, 412 uses the RFCOMM Bluetooth protocol (part of the Bluetooth protocol suite) to establish an RFCOMM 318, 418 wireless serial communication data channel that is operated by the Bluetooth-level stack. 316, 416 and which provides a simple reliable data stream that emulates a serial port connecting to a remote Bluetooth device (a radio adapter or Bluetooth device built into the radio) via an RFCOMM 346, 436 channel created by the application in the top layer Bluetooth stack 348, 434 in the Bluetooth radio device. In the symmetric case, the RFCOMM channel 436 is operated by the lower layer Bluetooth stack 432 on the Bluetooth radio chip 430. In the asymmetric case, the RFCOMM channel 346 is operated by the portion 344 of the upper layer Bluetooth stack (also called the Bluetooth layer stack intermediate) which includes the implementation of the RFCOMM protocol (and perhaps one or more different transport layer and network 5 protocols), but which excludes the implementation of the Application layer protocols, which are implemented in the upper layer Bluetooth stack 348 which handles the user interface applications.
    The Application layer of the top 10 stack 312, 412 then causes an autonomous stream connection 356, 456 to be formed (206) from the on-chip UART 314, 414 to the newly created RFCOMM channel 318, 418. UART for RFCOMM channel data path 356, 456 is a bidirectional "autonomous" flow connection (which bypasses the path through the upper layer Bluetooth stack 312, 412), which means that whatever data comes in on UART 314, 414 they are communicated over path 356, 456 to RFCOMM 318, 418 (and vice versa) without any intervention from any of the 20 upper layer Bluetooth stack and application layers 312, 412. Similarly, in the symmetric architecture (system 400), the Application layer in the upper layer Bluetooth stack 434 connects its newly formed RFCOMM channel 436 with its UART 438 via a similar autonomous stream connection 25 to form an autonomous bidirectional stream connection 46 0.
    In addition, the upper layer Bluetooth stack 412 associates (208) the RFCOMM 418 channel created in the peripheral device with the RFCOMM 436 channel created by the radio side from the learning point (using Bluetooth signaling during the initial connection of the peripheral device and connection with the Bluetooth radio apparatus) of a channel number that identifies the RFCOMM channel 436. This connects the autonomous stream connections 456, 460 from the perspective of the peripheral device to form the complete autonomous short-range wireless data path for data exchange of priority. Similarly, in the symmetric architecture, the upper layer Bluetooth stack 434 associates the RFCOMM channel 438 with the RFCOMM channel 418 by knowing (during Bluetooth signaling at the initial connection of the peripheral device and connection to the Bluetooth radio device) the channel number that identifies the RFCOMM channel 418. This connects the autonomous stream connections 460, 456 from the radio perspective to form the complete autonomous short range wireless data path for priority data exchange.
    As mentioned above, once these UART to RFCOMM connections have been formed, data entering one UART emerges from the other without any intervention from the higher level stack control layers 312, 412, 434. On the radio side, the data that emerge from the UART 438 are interpreted (decoded) by the external microcontroller 440 as a PTT signal 448 which is used to establish an event in the radio core to communicate the determined PTT state. For example, the PTT signal 448 determines a GPIO (Common Use Input/Output) on the radio or sends a message to another subsystem on the radio via a second data channel such as the secondary serial interface. Consequently, the entire UART to UART connection in system 400 is completely handled by the low-level Bluetooth stack 416, 432, and because of this, the incremental signaling latency is very low. In this symmetric case, the incremental latency between a byte entering a UART and a byte leaving the UART in the opposite RFCOMM connected system was observed to be less than 50 ms on average.
    In the asymmetric case (system 300), the upper layer Bluetooth stack 312 associates (208) the RFCOMM 318 channel created in the peripheral device with the RFCOMM 346 created by the radio side upon learning of a channel number that identifies the RFCOMM 346 channel to form, from the perspective of the peripheral device, the complete autonomous short range wireless data path for priority data exchange. Similarly, the upper layer Bluetooth stack 348 associates the RFCOMM channel 346 with the RFCOMM channel 318 to form, from a radio perspective, the complete autonomous short-range wireless data path for priority data exchange. On the radio side, the RFCOMM byte stream from the short range data path comprising the RFCOMM channels 318, 346 is directed to an internal software store 350 in the external microcontroller 340 which decodes the PTT state priority data and delivers a PTT signal corresponding 352 to the radio core. The latency observed in the asymmetric case is still very low (since the main cause of the latency in the prior art, which was latency resulting from processing in the upper layer Bluetooth stack in the peripheral device, is eliminated) and was observed to be less than 50 ms.
    Again, the established short-range wireless data path for priority data communication operates autonomously from an established wireless data path (210), by conventional Bluetooth signaling, through the upper layer Bluetooth stacks. 312, 348 and 412, 434 for non-priority data signaling transport for user interface applications that drive, for example, user input means such as voice. The data path for non-priority data is also referred to in the art as a SCO (Synchronous Connected Oriented) data link.
    Also, as indicated above, the RFCOMM to RFCOMM path is bidirectional, with the same performance in each direction. The uplink path (from radio to peripheral device) can be used for time sensitive high priority event signaling to the peripheral device. An example of a high priority uplink event is "radio suppressed noise". This signal can be used to control an audio power amplifier (PA) in a headphone (eg in a fast way such that the beginning of speech messages are not lost, meaning that the peripheral amplifier can be on within 50 ms (on average) of the radio activating an external audio AP or the radio core indicating to the wireless Bluetooth device that there is incoming audio active.
    In system 300, a noise state encoder 354 implemented in the external microcontroller 340 receives from the radio and encodes a noise state 370 which it sends via the autonomous path from RFCOMM 346 to RFCOMM 318 for decoding in the microcontroller 304, which provides a 360 noise state signal containing the noise state data to the peripheral device via a GPIO or other secondary serial connection. In system 400, microprocessor 440 receives from the radio and encodes a noise state 446 which it sends via the autonomous path from RFCOMM 436 to RFCOMM 418 for decoding in microcontroller 404, which provides a noise state signal. 444 containing the noise state data for the peripheral device.
    Turning to method 200 of Figure 2, when autonomous wireless data paths comprising wireless serial communication channels (for example, RFCOMM to RFCOMM paths) are established, priority data is detected (212) for sending through these channels, encoded (214) into a byte stream, and sent (216) over a novel short-range wireless data path created to prioritize data to another wirelessly connected device. In one embodiment, priority data (such as PTT state and noise state) is encoded in each data segment into a plurality of data segments provided by the serial interface device (eg, the UART), where each segment data has a selected byte size that depends on the specific, serial interface device implementation. In UART mode, the selected byte size is 1 byte. Consequently, in UART mode, priority data is encoded in each byte of the data stream provided to the UART. For example, each byte of data can be encoded by determining a set of bits (eg, one or more bits) in each byte to indicate priority data.
    Generally, priority data (for example, time-sensitive high-priority data) can be sent using less than the entire byte of data. Therefore, to more efficiently use the novel autonomous short-range wireless data path, the priority data is encoded with other data 358, 442, respectively, in microcontrollers 304, 404. The other data (which is also called "data of priority" since they are being sent via the autonomous path from RFCOMM to RFCOMM) include, but are not limited to, a state of a button, a state of an indicator (such as an LED), a state of a battery, a audio state. In a general sense, microcontrollers 304, 404 can be programmed with code to perform a novel encoding process comprising: receiving a first data stream generated from a button, indicator, etc. on the peripheral device, where the first data stream has a first size, - generate a second data stream to send (to the serial interface device) that has a second size that is larger than the first size by dividing the first stream of data in a number of data segments that have a selected byte size (for example, one byte in length); encode priority data into data segments; and sending the data segments with the encoded priority data to the other device.
    According to this novel encoding protocol, any number of compression schemes can be used whereby an original 8-bit data stream (of other data 358, 442) is encoded into multiple data segments each having less than all bits of the original 8-bit data stream. In one embodiment, a byte of a data stream of other data 358, 442 is split into two four-bit streams or two "half-byte" streams (thus, the novel protocol is called a "nibbler" protocol, which according to the term is used here refers to compression using two half-bytes and any other compression scheme) each encoded in a pair of two bytes, with the time-sensitive priority data (eg PTT state) being encoded in "extra /reserved" of each byte of the two-byte pair. In such a vessel, a nibbler data stream is approximately twice the length of the original data stream. To ensure that pressing PTT has priority over all other messages, the protocol reserves a bit, eg the top bit, of all bytes to indicate the state of the PTT. Also, a null message is used to indicate the state of the PTT if there is no other data to send. There is also a bit to indicate a HEADER so the stream can indicate half-byte length and SYNC. The alternative for length fields is to just use the header bit to indicate odd and even half-bytes. The radio runs a protocol to determine PTT status from the half-byte stream sent over RFCOMM channels. Then the microcontroller 340, 440 takes the lower two half-bytes of the arrival bytes and puts them together again to form a single byte which is sent for proper application on the radio.
    Figure 5 through Figure 8 illustrate tables to facilitate an exemplary implementation of the nibbler protocol. More specifically, Figure 5 to Figure 8, respectively, provide an illustrative implementation of the nibbler protocol format, exemplary headset protocol states, an exemplary null message, and exemplary messages with battery and button states. Referring to Figure 5, illustrative ranges for the fields comprise: PTT status = 1 bit, with a range 0.1; byte type = 1 byte, with a range of 0, 1, length = LEN 1*8 + LEN2 = 8 bits, with a range of 1-255 (0 is null message); and data = D1*8 + D2 = 8 bits, with a range of 0-255. It should be noted, however, that this is just an illustrative implementation of the nibbler protocol. Alternative implementations can be used. In one example, eg PTT state and the states of multiples (two or more, up to seven) other buttons and indicators can be encoded into each data segment (eg each data byte) using the nibbler protocol.
    In the preceding descriptive report, specific modalities were described. However, those of common knowledge in the art consider that various modifications and changes can be made without departing from the scope of the invention as set out in the claims below. Consequently, the descriptive report and figures are to be considered in an illustrative rather than a restrictive sense, and all such modifications are to be included within the scope of the present teachings. Benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage or solution or become more pronounced should not be considered as crucial, required or essential features or elements of any or all the claims. The invention is defined only by the appended claims including any amendments made while this application is pending and all equivalents of those claims as edited.
    Further in this document, relationship terms such as first and second, upper and lower, and the like may only be used to distinguish an entity or action from another entity or action without necessarily requiring or implying any such actual relationship or order between such entities or actions. The terms "comprises", "comprising", "has", "having", "includes", "including", "contains", "containing" or any other variation thereof, are intended to encompass a non-exclusive inclusion as such that a process, method, article, or equipment that comprises, has, includes, contains a list of elements not only includes those elements, but may include other elements not expressly listed or inherent in such process, method, article, or equipment. An element preceded by "comprises...a", "has...a", "includes...a", "contains...a" no, without further limitations, prevents the existence of additional identical elements in the process , method, article or apparatus which comprises, has, includes, contains the element. The terms "a" and "some" are defined as one or more unless explicitly stated otherwise herein. The terms "substantially", "essentially", "approximately", "about" or any other version thereof, are defined as close to as understood by those of ordinary skill in the art, and in a non-limiting modality the term is defined as being within 10%, in another mode within 5%, in another mode within 1%, and in another mode within 0.5%. The term "coupled" as used herein is defined as connected, though not necessarily directly and therefore necessarily mechanically. A device or structure that is "configured" in a certain way is configured in at least that shape, but it can also be configured in ways that are unrelated.
    It will be appreciated that some modalities may be comprised of one or more generic or specialized processors (or "processing devices") such as microprocessors, digital signal processors, custom processors and field-programmable gate arrays (FPGAs) and program instructions unique stores (including not just software such as firmware) that control the one or more processors to implement, together with certain non-processor circuits, some, most, or all of the method and apparatus functions for priority data signaling here described. Non-processor circuits may include, but are not limited to, a radio receiver, a radio transmitter, signal drivers, clock circuits, power supply circuits, and user input devices. As such, these functions can be interpreted as steps in a method for realizing priority data signaling described here. 30 Alternatively, some or all of the functions could be implemented by a state machine that has no stored program instructions or in one or more application-specific integrated circuits (ASICs), in which each function or some combination of some of the functions are implemented as special logic. Of course, a combination of the two approaches could be used. The state machine and the ASIC are considered here as a "processing device" for the purposes of the preceding discussion and claim language.
    Furthermore, an embodiment may be implemented as a computer-readable storage element or medium having computer-readable code stored therein to program a computer (e.g., comprising a processing device) to perform a method as described and claimed herein. Examples of such computer-readable storage elements include, but are not limited to, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (Read Memory), a PROM (Programmable Memory An EPROM (Erasable Programmable Read-only Memory), an EEPROM (Electrically Erasable Programmable Read-only Memory) and an instant memory. Furthermore, it is expected that those skilled in the art, despite possibly significant effort and many design choices motivated, for example, by available time, current technology, and economic considerations, when guided by the concepts and principles disclosed here will be easily able to generate such software instructions and programs and ICs with minimal experimentation. 28
    The Disclosure Summary is provided to enable the reader to quickly ascertain the nature of the technical disclosure. It is presented with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Also, in the Description
    Detailed Background, it can be seen that several features are grouped together in various modalities for the purpose of organizing the disclosure. This method of disclosure should not be interpreted as reflecting an intention that the claimed modalities require more features than are expressly cited in each claim. Rather, as reflected by the following claims, inventive subject matter falls within less than all 15 characteristics of a single disclosed modality. Thus, the following claims are hereby incorporated into the Detailed Description, with each independent claim as a separately claimed subject matter.
    权利要求:
    Claims (1)
    [0001]
    1. Method (200) for priority signaling via a wireless serial communication channel (318), the method (200) characterized in that it comprises: in a first communication device (102): establishing (210) a first short-range wireless data path to a second communication device (104) for exchanging non-priority data; establishing (208) a second short-range wireless data path to the second communication device (104), which is different from the first short-range wireless data path, for exchanging coded priority data in a byte stream , wherein the second short-range wireless data path comprises a wireless serial communication channel, further wherein the priority data comprises an indication of a push-to-talk (PTT) state bit encoded in the byte stream. , wherein both the first and second short-range wireless data paths are established by an upper layer of a protocol stack, in the first communication device (102), which includes an application layer, and additionally wherein the second established short-range wireless data path bypasses the upper layers of the protocol stack, which include the application layer when priority data is sent from the first communication device for the
    类似技术:
    公开号 | 公开日 | 专利标题
    BR112012003047B1|2021-05-18|method and apparatus for priority signaling over a wireless serial communications channel
    BR112012002943B1|2021-05-11|method and apparatus for determining and adjusting a push-to-talk state on a communication device
    CN109302372B|2021-02-23|Communication method, device and storage medium
    US20160359925A1|2016-12-08|Method and apparatus for transmitting and receiving data in wireless communication system
    EP3685561B1|2021-07-28|Proprietary link manager feature discovery and exchange
    KR101990489B1|2019-09-30|Method and apparatus for transmitting http data using bluetooth in wireless communication system
    KR102085175B1|2020-03-05|Method, apparatus, and system for adjusting data packet length in near field communication |
    WO2017024569A1|2017-02-16|Data transmission method, user equipment and base station
    KR20200119301A|2020-10-19|Audio data high-speed transmission method and apparatus
    WO2020109867A2|2020-06-04|Multi-mode communication device, method and system
    WO2020220795A1|2020-11-05|Data transmission method and apparatus
    WO2020220731A1|2020-11-05|Data transmission method and apparatus
    WO2018145292A1|2018-08-16|Communication method, device, and system
    WO2018103006A1|2018-06-14|Method and device for bluetooth linkage and bluetooth device
    WO2017177438A1|2017-10-19|Transmission method and apparatus for control information
    TW201943230A|2019-11-01|A method for transmitting or receiving a channel, a terminal device, and a network device
    CN113841441A|2021-12-24|Communication method and device
    WO2016154914A1|2016-10-06|Information transmission method, device and system
    同族专利:
    公开号 | 公开日
    WO2011019584A1|2011-02-17|
    AU2010282792B2|2013-09-05|
    US8554138B2|2013-10-08|
    AU2010282792A1|2012-03-01|
    CN102474545B|2014-07-23|
    AU2010282792B9|2013-09-19|
    US20110034126A1|2011-02-10|
    CN102474545A|2012-05-23|
    EP2465251A1|2012-06-20|
    CA2770198C|2014-04-01|
    EP2465251B1|2016-01-06|
    BR112012003047B8|2021-09-14|
    MX2012001778A|2012-03-21|
    CA2770198A1|2011-02-17|
    BR112012003047A2|2018-03-20|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US6789116B1|1999-06-30|2004-09-07|Hi/Fn, Inc.|State processor for pattern matching in a network monitor device|
    US7386000B2|2001-04-17|2008-06-10|Nokia Corporation|Packet mode speech communication|
    US7408948B2|2001-04-17|2008-08-05|Nokia Corporation|Packet mode speech communication|
    CA2431384C|2002-06-10|2009-08-04|Research In Motion Limited|Voicemail user interface methods and apparatus for mobile communication devices|
    US7688764B2|2002-06-20|2010-03-30|Motorola, Inc.|Method and apparatus for speaker arbitration in a multi-participant communication session|
    US20040198425A1|2002-10-01|2004-10-07|Mellone Charles M.|Establishing half-duplex audio link as battery saving means|
    US7260414B2|2003-12-08|2007-08-21|Kyocera Wireless Corp.|Optimized push-to-talk call setup|
    US7643856B2|2005-12-09|2010-01-05|Motorola, Inc.|Method for reducing apparent latency in linking a call received at a mobile communication device to a remote audio processor|
    KR101251193B1|2006-06-09|2013-04-08|삼성전자주식회사|METHOD AND SYSTEM FOR ESTABLISHING A GROUP SESSION IN PoC SYSTEM|
    US7801561B2|2006-09-28|2010-09-21|Sandisk Corporation|Methods of configuring a generic bluetooth controller of a flash drive to be compatible with multiple bluetooth peripheral devices|
    KR100791097B1|2006-11-29|2008-01-03|시코드 주식회사|Bluetooth remote ptt and handsfree communication system and method thereof|
    TWI371695B|2007-12-11|2012-09-01|Inst Information Industry|A priority-based data message publish method and system according to a data message chain|
    US8676636B2|2009-04-22|2014-03-18|Parkpod Gmbh|System for managing electric energy grid-vehicle exchange devices|
    US8554138B2|2009-08-10|2013-10-08|Motorola Solutions, Inc.|Method and apparatus for priority signaling over a wireless serial communication channel|
    US8417186B2|2009-08-10|2013-04-09|Motorola Solutions, Inc.|Method and apparatus for communicating push-to-talk state to a communication device|US8554138B2|2009-08-10|2013-10-08|Motorola Solutions, Inc.|Method and apparatus for priority signaling over a wireless serial communication channel|
    US8417186B2|2009-08-10|2013-04-09|Motorola Solutions, Inc.|Method and apparatus for communicating push-to-talk state to a communication device|
    US20110143664A1|2009-12-14|2011-06-16|Fuccello James R|System and method for bluetooth push to talk|
    WO2012062955A1|2010-11-12|2012-05-18|Maximilian Leroux|Mobile device control with external device|
    US8787256B2|2010-12-03|2014-07-22|Motorola Solutions, Inc.|Method and apparatus for ensuring transmission of critical data through a wireless adapter|
    TWM408094U|2010-12-29|2011-07-21|Deutron Electronics Corp|storage device|
    US9054781B2|2011-02-23|2015-06-09|Harris Corporation|Land mobile radio and adapter for use with standard mobile phone headset|
    US9385786B2|2011-12-14|2016-07-05|Marvell World Trade Ltd.|Method and apparatus for charging a battery in a mobile device through a near field communicationantenna|
    US20140108593A1|2012-10-15|2014-04-17|Dell Products L.P.|System and Method for Migration of Digital Assets|
    JP5969888B2|2012-10-16|2016-08-17|オリンパス株式会社|Wireless communication terminal, wireless communication method, and program|
    US10165612B2|2016-06-16|2018-12-25|I/O Interconnected, Ltd.|Wireless connecting method, computer, and non-transitory computer-readable storage medium|
    US9906893B2|2016-06-16|2018-02-27|I/O Interconnect, Ltd.|Method for making a host personal computer act as an accessory in bluetooth piconet|
    CN106601262A|2016-12-15|2017-04-26|北京塞宾科技有限公司|High definition Bluetooth audio frequency transmitting and receiving terminal and communication system|
    CN106851531A|2016-12-15|2017-06-13|北京塞宾科技有限公司|A kind of Bluetooth audio frequency transmission method|
    KR102044523B1|2017-08-22|2019-11-13|에스케이텔레콤 주식회사|Apparatus and method for providing short-range wireless communication|
    US10064021B1|2017-10-12|2018-08-28|Motorola Solutions, Inc.|Device and method for lower latency digital audio sample playback|
    KR102090800B1|2019-10-30|2020-03-18|에스케이텔레콤 주식회사|Apparatus and method for providing short-range wireless communication|
    法律状态:
    2019-01-15| B06F| Objections, documents and/or translations needed after an examination request according [chapter 6.6 patent gazette]|
    2020-01-14| B15K| Others concerning applications: alteration of classification|Free format text: AS CLASSIFICACOES ANTERIORES ERAM: H04M 1/725 , H04M 1/60 , H04W 4/10 , H04W 88/06 , H04L 29/06 , H04W 76/02 Ipc: H04W 4/10 (2009.01), H04W 76/45 (2018.01), H04L 29 |
    2020-01-21| B06U| Preliminary requirement: requests with searches performed by other patent offices: procedure suspended [chapter 6.21 patent gazette]|
    2021-04-13| B09A| Decision: intention to grant [chapter 9.1 patent gazette]|
    2021-05-18| B16A| Patent or certificate of addition of invention granted [chapter 16.1 patent gazette]|Free format text: PRAZO DE VALIDADE: 20 (VINTE) ANOS CONTADOS A PARTIR DE 06/08/2010, OBSERVADAS AS CONDICOES LEGAIS. PATENTE CONCEDIDA CONFORME ADI 5.529/DF |
    2021-09-14| B16C| Correction of notification of the grant [chapter 16.3 patent gazette]|Free format text: REF. RPI 2628 DE 18/05/2021 QUANTO AO QUADRO REIVINDICATORIO. |
    优先权:
    申请号 | 申请日 | 专利标题
    US12/538,505|2009-08-10|
    US12/538,505|US8554138B2|2009-08-10|2009-08-10|Method and apparatus for priority signaling over a wireless serial communication channel|
    PCT/US2010/044629|WO2011019584A1|2009-08-10|2010-08-06|Priority signaling over a wireless serial communication channel|
    [返回顶部]